Skip to main content

Terraform Variables Overview

In Terraform, variables are essential for creating flexible and reusable configurations. They allow you to manage dynamic values efficiently, making your infrastructure code more adaptable. Here's a breakdown of how Terraform variables work:

Types of Variables

  1. Input Variables: These are defined in .tf files and enable you to provide dynamic values to your configuration.
  2. Environment Variables: You can set values directly in your environment using the TF_VAR_ prefix (e.g., TF_VAR_variable_name=value).
  3. Output Variables: These are defined in output blocks, allowing you to pass values from one module to another or to display results after applying the configuration.

Declaring Variables

Variables in Terraform are declared using the variable block within .tf files. Here's an example:

variable "instance_type" {
  type        = string
  description = "The type of instance to launch"
  default     = "t2.micro"
}

Types of Variable Values

  • String: Used for text values.
  • Number: For numerical values.
  • Bool: For boolean values (true or false).
  • Complex Types: These include lists, maps, and objects, which allow for structured data.

Assigning Values

You can assign values to variables in different ways:

  • Default Values: Directly set within the variable block.
  • Command-Line Flags: Use the -var flag when running commands (e.g., terraform apply -var="instance_type=t2.large").
  • Files: Specify values in .tfvars files and load them using the -var-file option.

Variable Precedence

Terraform follows this order of precedence when determining which variable value to use:

  1. Command-line flags
  2. .tfvars files
  3. Environment variables
  4. Default values

Sensitive Variables

If you're working with sensitive data (like passwords), you can mask them in the output logs by setting sensitive = true in the variable definition. This ensures sensitive values are not exposed.

By leveraging variables in Terraform, you can easily adjust your infrastructure configuration without needing to modify the core code. This makes your code more modular and adaptable to different environments or scenarios.

Comments

Popular posts from this blog

A Complete CI/CD Pipeline

Complete CI/CD Pipeline Using GitHub, Jenkins, Maven, SonarQube, Nexus, and Docker A well-designed CI/CD pipeline plays a critical role in modern DevOps practices by automating software delivery, improving code quality, and reducing deployment risks. In this article, I will explain how I build an automated CI/CD pipeline using GitHub, Jenkins, Maven, SonarQube, Nexus Repository, Docker, and Docker Hub. Source Code Management with GitHub The CI/CD workflow begins with storing the application source code in GitHub. Developers regularly push code changes or create pull requests to collaborate on features and bug fixes. Whenever new code is pushed to the repository, GitHub triggers Jenkins automatically through a webhook. This integration helps start the CI/CD pipeline without manual intervention. Code Checkout Stage in Jenkins The first stage of the pipeline is the checkout process. Jenkins connects to the GitHub repository and pulls the latest version of the source code. ...

Terraform for AWS: Step-by-Step Infrastructure Automation That Actually Works

How I Use Terraform to Provision and Manage AWS Infrastructure Efficiently Infrastructure as Code (IaC) has become a critical part of modern cloud operations, and Terraform is one of the most popular tools for automating cloud infrastructure deployment. In this article, I'll share how I use Terraform to build and manage AWS resources such as Virtual Private Clouds (VPCs), EC2 instances, Application Load Balancers (ALBs), and Auto Scaling Groups. Building AWS Infrastructure with Terraform My infrastructure deployment process begins by defining all AWS resources as code. This approach ensures consistency, repeatability, and easier management across multiple environments. The first step is creating a secure network architecture using a VPC. Within the VPC, I configure public and private subnets, route tables, internet gateways, and other networking components required for application deployment. Once the networking layer is ready, I deploy EC2 instances inside private su...

Master Linux Administration for DevOps: Powerful Commands, Troubleshooting Tips & Best Practices

Linux administration is one of the most important skills for anyone working in DevOps. From application servers and CI/CD platforms to containers and cloud infrastructure, Linux-based systems are widely used in modern technology environments. In my day-to-day DevOps activities, I regularly work with Linux commands to manage files, monitor processes, troubleshoot services, investigate network problems, analyze logs, and resolve production issues. This guide covers essential Linux administration concepts and commands that are useful for DevOps engineers, along with practical examples of how they can be applied during everyday troubleshooting. 1. Understanding Linux File Permissions Linux uses a permission system to control access to files and directories. The three basic permissions are: Read (r) – Allows a user to view the contents of a file or directory. Write (w) – Allows modifications to a file or directory. Execute (x) – Allows a file to be executed or a director...